workaround xtrabackup error using mysql global variable old_alter_table #8340
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Resubmission of #8317
Instead of backporting commits into earlier versions, we want to apply changes in earlier versions, then merge forward.
This will merge into
release-9.0
branchCopy of original comment from @deepthi :
Description
Some of the xtrabackup tests have been flaky for a while. Today @vmg was able to extract the actual error from a failing test.
This seems to be a known issue with a documented workaround. Implementing the workaround.
https://www.percona.com/blog/2017/08/08/avoiding-the-an-optimized-without-redo-logging-ddloperation-has-been-performed-error-with-percona-xtrabackup/
The blog post has 3 suggestions:
--lock-ddl
: only works with Percona MySQL server, we are running community MySQL server in CI--lock-ddl-per-table
: did not fix the problemold_alter_table
: 🤞Related Issue(s)
Fixes #8315
Checklist
Deployment Notes